Pid runtime deadband actions docs next#6267
Closed
ngolf wants to merge 64 commits intoesphome:currentfrom
Closed
Conversation
…#6076) Fix 5 component entries in index.mdx that were missing leading slashes and trailing slashes in URLs, and had inconsistent spacing. Add missing key_collector.svg image. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* Fix blank guides/changelog and guides index pages The Hugo-to-Starlight migration stripped the redirect shortcode from guides/changelog.mdx, leaving a blank page. The guides/index.mdx was also empty since Hugo auto-generated section listings but Starlight does not. - Add /guides/changelog/ redirect to latest changelog in astro.config - Remove empty guides/changelog.mdx stub (redirect replaces it) - Populate guides/index.mdx with categorized links to all guide pages Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add changelog pages to pagefind search index The pagefind glob only indexed components, cookbook, guides, projects, and web-api. Changelog pages were not searchable. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Revert "Add changelog pages to pagefind search index" This reverts commit ffbd3bb. * Enable pagefind search indexing for changelog index page This allows searching for "changelog" to return the changelog index, giving users a way to discover changelogs via site search. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* Make changelog index a real searchable page Replace the /changelog/ redirect with a LatestChangelog component that dynamically renders the latest changelog content at build time. This makes the changelog index discoverable by pagefind search while still showing the latest release content. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add client-side redirect to latest changelog The index page renders the latest changelog content for pagefind searchability, then immediately redirects visitors to the dedicated changelog page via client-side JS. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Expand changelog index description for search results Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Apply suggestion from @swoboda1337 --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…32-C2/C61 no RMT support (esphome#6086) Update docs for ESP32-C2 and ESP32-C61 which lack RMT hardware: - esp32_rmt_led_strip: Add note that C2/C61 are not supported - remote_transmitter/receiver: Note C2/C61 use software fallback, rename ESP32 config section to ESP32 RMT config, remove C61 from RMT memory tables Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…e#6087) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…#6107) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…phome#6109) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: J. Nick Koston <nick@home-assistant.io>
Co-authored-by: Jonathan Swoboda <154711427+swoboda1337@users.noreply.github.com>
Co-authored-by: Martin Ebner <martinebner@me.com> Co-authored-by: Jonathan Swoboda <154711427+swoboda1337@users.noreply.github.com>
…SP32-only (esphome#6104) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Jonathan Swoboda <154711427+swoboda1337@users.noreply.github.com>
![esphome[bot]](https://avatars.githubusercontent.com/in/247347?s=60&v=4){kind=small}
There was a problem hiding this comment.
As this is a feature matched with a PR in https://github.com/esphome/esphome, please target your PR to the next branch and rebase.
There was a problem hiding this comment.
As this is a feature matched with a PR in https://github.com/esphome/esphome, please target your PR to the next branch and rebase.
Author
|
Closed as created off wrong branch. |
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Update docs for esphome PR14730.
Add action climate.pid.set_deadband_control_parameters_multipliers
Add sensors K{P,I,D]_DEADBAND_MULTIPLIER
Pull request in esphome with YAML changes (if applicable):
Checklist
I am merging into
nextbecause this is new documentation that has a matching pull-request in esphome as linked above.or
I am merging into
currentbecause this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.Link added in
/src/content/docs/components/index.mdxwhen creating new documents for new components or cookbook.New Component Images
If you are adding a new component to ESPHome, you can automatically generate a standardized black and white component name image for the documentation.
To generate a component image:
Comment on this pull request with the following command, replacing
component_namewith your component name in lower_case format with underscores (e.g.,bme280,sht3x,dallas_temp):The ESPHome bot will respond with a downloadable ZIP file containing the SVG image.
Extract the SVG file and place it in the
/public/images/folder of this repository.Use the image in your component's index table entry in
/src/content/docs/components/index.mdx.Example: For a component called "DHT22 Temperature Sensor", use:
Note: All images used in ImgTable components must be placed in
/public/images/as the component resolves them to absolute paths.